Product Copy

The OIRW application introduces a new Product Copy option under the Tools main menu. This utility allows authorised users to quickly create a new product by reusing an existing product’s setup—such as configuration data, business rules, transactions, and segments—so they can replicate a product from one company/product hierarchy structure to another without rebuilding the setup from scratch.

The Product Copy utility enables users to selectively copy a product to another subsidiary company or product hierarchy. By leveraging the existing product setup data, users can selectively reuse and copy the following across environments or organisational structures:

  • Business Rules

  • Transactions

  • Segments

  • Product Funds

  • Comment Templates

  • Related product setup configurations

Note: The system displays all configured target environments that have IVS enabled and are linked to the same IVS as the source environment.

Security Privilege - Only users assigned to a security role with the required privilege can access the Product Copy option. To support this functionality, a new privilege is introduced in the IVSPRIVILEGE entity with the following details:

Field Value
PRIVILEGENAME Utilities-ProductCopy
Description Allow access to Product Copy Tool

Prerequisite: To access the Product Copy option, a user must be assigned to a security role that possesses the Utilities-ProductCopy privilege. If the user lacks this privilege, the system prevents the product copy operation and displays an error message.

Product Copy Workflow

  • Log in to the Oracle Insurance Rules Workbench using valid credentials.

  • Select the target environment.

  • Navigate to the Tools menu from the top-right corner and select Product Copy.

  • Clicking the Product Copy option displays a guided step-by-step workflow along with the configured target environments. If no additional environments are configured, the initially selected environment is displayed by default.

Product Properties

  • Select the target environment to enable source product selection.

  • The system displays the product properties screen, where all required inputs must be updated.

  • Select a primary company from the list of available primary companies in the environment.

  • Select a subsidiary company; the drop-down displays subsidiaries under the chosen primary company.

  • Select a product available under the selected subsidiary company.

  • Under Target Properties, select a primary company from the list available in the target environment.

  • Select a subsidiary company from the available subsidiaries under the chosen primary company.

  • Select a target product under the selected subsidiary company (optional).

  • Enter a New Product Name. By default, the value matches the source product name.

  • If a product with the same name already exists, the system displays an error requiring a different product name.

  • If a target product is selected, the system copies the source product under the selected target product.

  • If no target product is selected, the system copies the source product under the selected subsidiary company.

  • Optionally, select Create Config Package Only to generate only a configuration package without performing the product copy operation.

Note: By default, the system leaves the Create Config Package Only option unchecked. When the user selects this option, the system generates only the configuration package and does not copy the product setup data or business rules. The user can then deploy the generated configuration package using the standard or detached migration process.

Preserve GUIDs and copy all rules

Preserve GUIDs

Note: This option is available only when the source product and target product belong to different environments. If both products belong to the same environment, the system leaves the Preserve GUIDs option unchecked and disables it.

When the user selects Preserve GUIDs:

  • The system auto-populates the Product Name field with the source product name.

  • The Product Name field becomes disabled.

  • The following GUIDs are preserved:

    • ProductGUIDs

    • BusinessRuleGUIDs

    • TransactionGUIDs

    • SegmentNameGUIDs

Conditional Behaviour:

  • If the source and target environments are the same, the system disables the Preserve GUIDs option.

  • If the user selects Copy All Rules, the system skips directly to the Release Management step.

  • If this option is not selected, the system guides the user through the rule selection process.

Rule Selection

The system navigates to the list of rules page where the required rules can be selected.

Next, the Rule Details page displays the Available Rules and Assigned Rules sections. Based on the selected options, the system navigates the user through additional setup selection screens. Users can move rules between the sections using the arrow controls and then click Next to proceed.

After defining the product properties, users can optionally review and select the setup components that should be included in the product copy operation. These selections determine the final configuration data included in the generated configuration package and copied product setup.

Release Management

The workflow then navigates to the release management page where users can either,

  • Add a new configuration package, or

  • Select an existing configuration package from the available list.

  • When an existing configuration package is selected, the generated product copy components are appended to the selected package.

  • If the user selects Create Config Package Only in the previous steps, the system automatically enables the Add To Configuration Package option and disables further modification of this setting.

The Product Copy configuration package can be deployed using either normal migration or detached migration.

Any DML scripts included as part of the package must be executed manually before deploying the configuration package. These scripts contain product relationship hierarchy information. If hierarchy changes are required, users can manually modify the DML scripts before execution.

Review and Completion

The final step displays the Review and Complete page summarising the following:

  • Applied rules

  • Selected transactions

  • Assigned segments

  • Product funds

  • Comment templates

  • Assigned privileges

  • Package details

Users can verify the details and click the following:

  • Finish to proceed with the product copy process, or

  • Cancel to abort the operation.

Clicking Finish displays a confirmation dialogue box.

After confirmation, the system displays a success message indicating that the product copy request has been submitted successfully.